System and Methods for Data Communications in a Wireless Communication System

ABSTRACT

Techniques for use by a mobile device configured to operate in a wireless network for the communication of data messages with a server are described. When the mobile device does not have an open session with the server, the mobile device receives from a service node via the wireless network a message which informs the mobile device that a data message has arrived at the server and needs to be retrieved. The message includes an identifier which identifies the data message at the server. In response to opening an application at the mobile device, the mobile device communicates directly with the server via the wireless network for retrieving the data message. This involves commencing an open session with the server, sending to the server a command for retrieving the data message, and receiving from the server the data message in response to sending the command. The mobile device may use the identifier for retrieving the data message from the server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/716,011 filed Sep. 26, 2017 by David Clark, et al. entitled, “Systemand Methods for Data Communications in a Wireless Communication System”(Atty. Docket No. 30561-US-CNT[7]-4214-58908), which is a continuationof U.S. Pat. No. 9,794,770 issued on Oct. 17, 2017, which is acontinuation of U.S. Pat. No. 9,549,311 issued on Jan. 17, 2017, whichis a continuation of U.S. Pat. No. 8,918,084 issued on Dec. 23, 2014,which is a continuation U.S. Pat. No. 8,320,900 issued on Nov. 27, 2012,which is a continuation U.S. Pat. No. 8,090,363 issued on Jan. 3, 2012,which is a continuation of U.S. Pat. No. 7,848,751 issued on Dec. 7,2010, which is a continuation of U.S. Pat. No. 7,630,714 issued on Dec.8, 2009, which claims priority to and benefit of U.S. ProvisionalApplication No. 60/734,448 filed Nov. 8, 2005 by David Clark, et al.entitled, “System and Methods for Data Communications in a WirelessCommunication System”, all of which are incorporated by reference hereinas if reproduced in their entirety.

TECHNICAL FIELD

This invention relates to wireless communication techniques in general,and a system and methods for configuring data communications in awireless communications system in particular.

BACKGROUND

User mobility has always been a hallmark of cellular phones and morerecently data enabled mobile devices. The ability to travel with amobile device wherever desired is increasingly becoming a must havefeature for mobile device users. Manufacturers are not ignorant of theseuser demands and offer mobile devices which can be used throughout muchof the world. Network carriers are also not ignorant of these marketpressures and so they offer their users the ability to roam with theirdevices and maintain service, through roaming agreements with othernetwork carriers. A user may take their mobile device from their homecountry or region and travel elsewhere and still receive service from aforeign network carrier.

It is not necessary for all network carriers to provide the same set offunctionalities and services. A network carrier in one country may nothave enough demand from their users to offer a service. A region'spopulace or customer base may not be willing to pay sufficient amountsof money to induce a network carrier into offering a feature.Alternatively, a country may not allow certain services based onreligious ideals or because of legal requirements.

It is possible for a user of a mobile device to gain service from aforeign network carrier temporarily, while, for example, on a businesstrip. It is also possible for changes in a country's legal system or fora populace's tastes to change. As such, a mechanism is required toforcefully, easily and automatically alter the services and/or thefeatures offered to and the behaviour of a mobile device, or devices,based on the location and abilities of the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention will be obtained byconsidering the detailed description below, with reference to thefollowing drawings:

FIG. 1 is an exemplary environment in which a wireless communicationsystem and method in accordance with a preferred embodiment may bepracticed;

FIG. 2 depicts additional details of an exemplary relay networkinfrastructure operable as part of the wireless router system of FIG. 1;and

FIG. 3 is a communications sequence diagram describing an exemplarysystem and method for wireless messaging between a host service and amobile communications device of FIG. 1.

DETAILED DESCRIPTION OF THE DRAWINGS

The present invention will now be described with reference to variousexamples of how the embodiments can best be made and used. Likereference numerals are used throughout the description and several viewsof the drawings to indicate like or corresponding parts, wherein thevarious elements are not necessarily drawn to scale.

In an embodiment is disclosed a method for enabling wireless datacommunications between a first and a second communications device, themethod comprising providing location information and capabilityinformation associated with at least one of the first and secondcommunications devices based on said provided location information andsaid provided capability information, providing a mask and selectivelyenabling wireless data communications based on said mask.

In another embodiment is disclosed a method for enabling wireless datacommunications at a communications device, the method comprising sendinglocation information and capability information associated with thecommunications device to selectively enable wireless data communicationssubsequent to said sending of said location information and saidcapability information, sending a data message from the communicationsdevice in response to the data message sent, receiving an enablementresponse selectively sending a subsequent data message from thecommunications device based on said enablement response.

In yet another embodiment is disclosed a system for enabling wirelessdata communications between a first and a second communications device,the system comprising a communication module adapted to provide locationinformation and capability information associated with at least one ofthe first and second communications devices and an enablement moduleadapted to provide a mask based on said provided location informationand said provided capability information wherein the enablement moduleis further adapted to selectively enable wireless data communicationsbased on said mask.

In yet another embodiment is disclosed a system for enabling wirelessdata communications at a communications device, the system comprising aconfiguration communication module adapted to send location informationand capability information associated with the communications device anda data communication module adapted to send data messages from thecommunications device wherein the configuration communication module isfurther adapted to receive an enablement response in response to a datamessage sent and wherein the data communications module is even furtheradapted to selectively send another data message from the communicationsdevice based on said enablement response.

In yet another embodiment is disclosed a method for configuring wirelessdata communications at a communications device, the method comprisingsending location information and capability information associated withthe communications device in response to the location information andcapability information sent, receiving configuration information andselectively configuring wireless communications at the communicationsdevice based on said configuration information.

FIG. 1 is an exemplary environment in which a wireless communicationsystem 100 in accordance with a preferred embodiment may be practiced.The exemplary wireless communication system 100 includes a plurality ofhost services (three shown, 102, 104, and 106), each of which may have aplurality of services such as, but not limited to, e-mail, calendar,Internet web browser, and other applications, available to theirsubscribers. In this particular example, the host services 102, 104, and106 are typically configured as servers, each containing at least oneprocessor, a storage means and each using a network interface over whichcommunications with a communication network 108 such as the Internet canbe effectuated. The host services 102, 104 and 106 send and receivemessages over communications network 108 to and from wireless routersystem 110 allowing communication between the host services 102, 104,and 106 and the wireless router system 110.

The wireless router system 110 is connected to a plurality of wirelessnetworks (three shown, 114, 116, and 118), each of which may support aplurality of mobile devices (one in each wireless network is shown, 120,122, and 124). The wireless networks 114, 116, and 118 may be a cellulartelephone network, such as a global system for mobile communication(GSM) network, or a code division multiple access (CDMA) network, atwo-way paging network, a short range wireless network such asBluetooth™ and IEEE 802.11 compliant network, and others alike, and themobile devices 120, 122, and 124 are devices compatible with thecorresponding wireless network.

Mobile communications devices 120, 122 and 124 are two-way communicationdevices with advanced data communication capabilities having thecapability to communicate with other mobile devices or computer systems,such as host services 102, 104, 106, through a network of transceiverstations, including wireless router 110 and communication network 108.The mobile communication devices 120, 122 and 124 may also have thecapability to allow voice communication. Depending on the functionalityprovided, it may be referred to as a data messaging device, a two-waypager, a cellular telephone with data messaging capabilities, a wirelessInternet appliance, or a data communication device (with or withouttelephony capabilities). The preceding list is not meant to beexhaustive; the embodiments described herein can be practised with anytype of mobile device, whether listed above or not. In the example shownin FIG. 1, mobile communications devices 120, 122 and 124 each contain aprocessor, a radio, an information storage means and at least onesoftware module adapted to perform tasks. In a preferred embodiment,mobile communications devices 120, 122 and 124 are capable of sendingand receiving messages using the radio. Also in the preferredembodiment, the at least one software module includes an event generatormodule, adapted to generate events, and a communications module, adaptedto send and receive messages using the MCD's radio.

Mobile communications devices are generally capable of communicatingover multiple communication channels. For example, SMS messages arriveover the voice communication channel, whereas email messages arrive overa data communication channel. In a preferred embodiment enable messages(327 and 336) are received at MCD 120 using the same communicationchannel as is used by MCD 120 to receive the entire message (348 and351). As explained above, the MCD 120 includes modules, software forexample, which are adapted to perform various tasks when executed in MCD102's processor. In one embodiment, the MCD 120 contains both acommunication module and an event generator module. The communicationmodule is adapted to execute in MCD 120's processor and in cooperationwith the MCD 120's radio is capable of sending and receiving messages.The event generator module is also adapted to execute in MCD 120'sprocessor and is capable of generating events in one of two ways: usergenerated events and device generated events. User generated eventsinclude such things as the user of MCD 120 opening a messagingapplication resident in MCD 120, such as an email application, the userof MCD 120 rolling a wheel input device, such as a thumbwheel, the userof MCD 120 pressing a key on MCD 120's keyboard, the user of MCD 120logging in to MCD 120 or the user of MCD 120 electing to maintain ansession active by responding to a prompt from MCD 120. Device generatedevents include such things as the expiry of a timer, MCD 120 generatinga ping message to keep a session alive with the network or MCD 120commencing a data session, such as a PDP context, with a network.

One of the primary purposes of host services 102, 104 and 106 is toprocess information received from other sources, such as mail servers(not shown) and mobile communications devices 120, 122, 124, and sendthe information on to the appropriate recipient, typically a differenthost service 102, 104, 106, mail server or mobile communications device120, 122 or 124. Host services 102, 104 and 106 are configured to sendand receive email messages and as such typically communicate with a mailserver. Mail servers could include for example a Microsoft® Exchange®server, a Lotus® Domino® server, a Novell® GroupWise® server, an IMAPServer, a POP Server or a webmail server or any other mail server aswould be understood by those in the art. The host services 102, 104 and106 also contain a software module, which executes in their processor toachieve the desired sending and receiving of messages as well as theappropriate processing of information. In a preferred embodiment thesoftware module of each host service 102, 104, 106 is a messagingmodule, the messaging module is adapted to receive messages from atleast one external mail server, send messages to mobile communicationsdevices 120, 122, 124, receive messages from the same mobilecommunications devices and send messages to the at least one externalmail server(s). The at least one external mail server(s) could also beat least one mobile data server(s) for example. The wireless routersystem 110 may also be directly connected to a host service, such as alocal service 112, without the communication network 108. In anotherembodiment, it is possible for host services 102, 104 and 106 tocommunicate directly with mobile communications devices 120, 122 and124, in this embodiment, host services 102, 104 and 106 must be capableof addressing communications to mobile communications devices 120, 122and 124 without the aid of the wireless router system 110.

In the environment described in FIG. 1, messaging occurs between mobilecommunications devices 120, 122 and 124 and host services 102, 104 and106. It is possible for mobile communications devices 120, 122 and 124to send messages to and receive messages from host services 102, 104 and106. As an example, when a message is received by any one of hostservices 102, 104, 106, the intended recipient, mobile communicationsdevices 120, 122 and 124 is informed by the host service 102, 104 and106 that a message has arrived which needs to be retrieved by way of anenable message. Host service 102, 104 and 106 may send a plurality ofenable messages to mobile communications device 120, 122 and 124 or hostservice 102, 104 and 106 may choose to send one enable message untilmobile communications device 120, 122 and 124 fetches the pendingmessage(s). A fetch command is issued by the mobile communicationsdevice 120, 122 and 124 upon the generation of an event by an eventgenerator after an enable message has been received and is sent to hostservice 102, 104 and 106. The generated event and the enable message areindependent and neither one influences the occurrence or likelihood ofthe other. When host service 102, 104 and 106 receives a fetch command,host services 102, 104 and 106 will send the pending message or messagesto mobile communications device 120, 122 and 124 which issued the fetchcommand. Both the enable messages and the fetch message may or may notcontain message identifiers. A message identifier uniquely identifies amessage for mobile communications devices 120, 122 and 124 and allowsmobile communications devices 120, 122 and 124 to retrieve specificmessages. The host service 102, 104, 106 may send all pending messagesshould multiple messages be pending for the mobile communications device120, 122 and 124 which issued the fetch command.

FIG. 2 depicts additional details of an exemplary relay networkinfrastructure 200 operable as part of wireless router system 110 (fromFIG. 1) described above. A relay services node 202 is operable, at leastin part, for providing connectivity between mobile communication devices120, 122, 124 and various data application services (host services 106,Internet Access Provider/Internet Service Provider server 204,peer-to-peer server 210 and other gateways 206 for example), regardlessof the geographic location of the mobile communications devices 120,122, 124 and their respective wireless carriers. Relay services node 202comprises a communication module and an enablement module (not shown).The communication module is adapted to provide or receive informationfrom other sources, the information comprising location and capabilityinformation sent from communications devices. The enablement module isadapted to provide or create a mask based on the information received bythe communication module, the mask being used to enable or disable datacommunications. Also, since multiple relay services nodes can co-existin a distributed network architecture, a relay bridge 208 may beprovided in operable connection with the relay services node 202 forsupporting inter-relay connectivity. In one implementation, relay bridge208 connects with separate relay node sites, forming tunnels betweenrelays over which mobile communication device messages can flow to andfrom host services 102, 104, 106, irrespective of the region where themobile communications device 120, 122, 124 is in.

Communication between the relay services node 202 and variousapplication gateways and servers is effectuated using any suitableprotocol, e.g., Server Relay Protocol (SRP), preferably over InternetProtocol (IP) links. By way of illustration, host service 102 (fromFIG. 1) associated with the communication network 108 (from FIG. 1)sends information to and receives information from relay services node202 using SRP. Relay services node 202 in turn sends information to andreceives information from mobile communications devices 120, 122 and124. Likewise, reference numerals 204 and 206 refer to externalapplication gateways, such as Internet Service Provider (ISP) orInternet Access Provider (IAP) servers, and other gateways,respectively, which are also interfaced with the relay services node 202using SRP. A peer-to-peer server 210 may also be provided in operableconnection with the relay services node 202 for handling peer-levelmessaging between two mobile communication devices 120, 122, 124 usingtheir respective PIN indicia.

Additionally, a database 211 may be provided in operable connection withthe relay services node 202 for handling and managing mobilecommunication device location and capability information. Preferably,this location and capability information is stored in records by PINindicia of the mobile communication devices 120, 122, 124, which may beprogrammed into the devices at the time of manufacture or dynamicallyassigned afterwards, wherein the stored records maintain a particulardevice's last known location and capabilities. A registration server 216is operable for providing registration services for mobile communicationdevices 120, 122, 124 when they are initially activated or when the userre-registers due to moving to a different wireless network coveragearea. In one implementation, the address information of registrationserver 216 may be programmed into the mobile communication devices 120,122, 124 to locate, contact and register with registration server 216.When a mobile communications device 120, 122, 124 registerssuccessfully, registration server 216 is operable to provide relayservices node 202's location, whereupon data sessions may be engaged bythe mobile communications device 120, 122, 124. Further, a database 217is associated with the registration server 216 for storing a PINauthentication key provided by the mobile communication device duringits registration with the network. The PIN authentication key may beused by the network in securing the PIN indicium of a mobilecommunication device 120, 122, 124 so that it can be ensured thatpackets are delivered to or received from a legitimate mobilecommunication device (i.e., with a valid PIN) instead of a device thathas illegally accessed or stolen a PIN or managed to impersonate, orspoof, a PIN.

One or more wireless transport (WT) interfaces are provided as part ofrelay services node 202 for connecting with the wireless carriernetworks that service mobile communication devices 120, 122, 124. By wayof illustration, WT 212A and WT 212B communicate with respective packetrouters 214A and 214B using TCP/IP links, which route data packets toand from respective wireless packet data service networks, exemplifiedin FIG. 2 as carrier network 220A and carrier network 220B.

Continuing to refer to FIG. 2, registration server 216, which handlesadministration and registration services for mobile communicationdevices 120, 122, 124, may also be provided with separate WT and packetrouting for interfacing with the carrier networks 220A, 220B, althoughnot specifically shown. A provisioning system (PRV) 218 may beco-located or otherwise associated with the relay services node 202 forsetting up and managing various service providers (i.e., carriernetworks), subscribers, mobile communication device manufacturers,resellers, and other entities in order to support any number of serviceand market differentiation requirements. Additionally, the provisioningsystem 218 may include logic for provisioning personalized indicia(e.g., PIN assignment and management) with respect to the mobilecommunication devices 120, 122, 124. Also, subscriber validation logicmay be provided as part of the provisioning system 218. PRV 218 andrelay services node 202 may additionally include logic and storage meansintended to track the current state of individual or groups of mobilecommunication devices 120, 122, 124 as well as the current state ofindividual or groups of host services 102, 104 and 106. The currentstate information to be stored, preferably in a cache or database 211,may include such information as location, capabilities and mask values.In a preferred embodiment, mobile communications devices 120, 122 and124 report their location and capabilities to registration server 216which passes the information on the relay services node 202. Also in apreferred embodiment, host services 102, 104 and 106 report theirlocation and capabilities directly to relay services node 202. In apreferred embodiment, mask values (masks) are determined by relayservices node based on the received location and capabilities data.These masks are stored in association with an identification of theoriginator of the information and are used to determine the originator'saccessibility to certain services, including but not limited to emailservice and any other data service. Using the masks, relay services 202can decide, for example, whether to pass on a data communicationreceived from a given mobile communications device 120, 122, 124 or dropthe communication and send a negative acknowledgment to the sender.Alternatively, the masks, or a portion of the masks, could be sent tomobile communications device 120, 122, 124 or to host service 102, 104,106 so that mobile communications device 120, 122, 124 or to hostservice 102, 104, 106 can filter their own data communications beforesending data communications to relay services 202. Current stateinformation, such as location, capabilities and masks, can be updatedthrough communication with registration server 216, communication with amobile communication device 120, 122, 124 or communication with hostservices 102, 104, 106. In another embodiment, the current stateinformation could be stored at WT 212A and 212B.

Reference is now made to FIG. 3, where there is shown an exemplaryembodiment of how a configuration communication session between mobilecommunications device (MCD) 120, 122, 124, host services 102, 104, 106,relay services node 202, provisioning server 218 and registration server216 may be carried out to properly configure communications between MCD120, 122, 124, relay services node 202 and host services 102, 104, 106.Before describing the message flow shown in FIG. 3, a detaileddescription of the participants and the individual messages themselvesis first provided below.

Labelled participants in this flow diagram are: the mobilecommunications device (MCD) 120 (which could also be any of wirelesscommunications devices 122 and 124), relay services node 202 and hostservices 102 (which could also be any of host services 104 and 106),provisioning server 218 and registration server 216. In this particularexample, mobile communications device 102 and host services 120 discloselocation and capability information to relay services 202. Thisdisclosure enables relay services 202 to decide whether or not it willallow certain types of data communications, email for example, to passthrough relay services 202 when destined to or originated from mobilecommunications device 102 and host services 202.

To initiate proper configuration of MCD 120, communication 305 is sentto register mobile communications device 120 with registration server216. Communication 305 contains registration information and is sentfrom mobile communications device 120 to registration server 216containing such information as device location and capabilityinformation. Device location information as contained in communication305 is an indicator of the geographic location wherein mobilecommunications device 120 is currently located. The device locationinformation which can be, for example, an IP address or network providercode is discussed in further detail below. Device capability informationas contained in communication 305 could be any indicator of mobilecommunications device 120's ability to support or comply with featuresor protocols and for example may include a number to indicate at whichlevel mobile communications device 120 is compliant to a specifiedprotocol (protocol support information) or a listing of which featuresmobile communications device 120 does support or is capable ofsupporting (feature compliance information).

In communication 310, registration server 216 replies to communication305 with a registration response. This registration response includessuch information as resource access addresses, associated lists ofnetwork access addresses and capability fields associated with eachnetwork access address. The capability fields associated with eachnetwork access address include such information as whether or not MCD120 should expect to operate in a given mode when communicating with theresource specified by the resource access address when using the networkspecified by the network access address. Registration server 216 alsoprovides communication 315 to provisioning system 218 which passes onthe relevant information, including location and capabilities, receivedfrom mobile communications device 120 in communication 305. Thisinformation is stored at provisioning system 218 and can be used todetermine future behaviour and communications between the provisioningsystem 218 and MCD 120. This information is also passed to relayservices 202 as communication 317. Relay services 202 stores thisinformation in a database or in a cache for example, and utilizes thisinformation to, for example, determine whether mobile communicationsdevice 120 is allowed access to certain services, such as email or webbrowsing for example.

In a preferred embodiment, relay services 202 uses the device locationand capability information received in communication 317 to create andstore a mask associated with mobile communications device 120. This maskis used, at least in part, to determine whether subsequent data messagesreceived from and/or destined to mobile communications device 120 areallowable. For example, if a data message received from MCD 120 isallowable, relay services 202 sends the message on to the intendedrecipient. If the data message is not allowable, relay services 202considers whether mobile communications device 120 has been providedwith enough warnings, or time, to stop sending subsequent data messagesby further examining the mask for an indication that a warning isrequired or by examining a warnings monitor. If relay services 202determines that mobile communications device 120 has been provided withenough warnings, or time, to cease sending subsequent data messages,relay services 202 drops subsequent data messages and send a negativeacknowledgment to mobile communications device 120. If, prior to sendingan allowable data message, relay services 202 determines that mobilecommunications device 120 has not been give sufficient warning, or time,relay services 202 sends the data message on to the intended recipient,sends a warning to mobile communications device 120, updates a warnings,or time, monitor and mobile communications device 120 provides anotification to the user of mobile communications device 120 that theyare or will be in the future restricted from sending any subsequent datamessages. Mobile communications device 120, upon receipt of the warning,optionally restricts the user from further attempts to send datamessages. The warnings monitor can be any value stored in a data storeand associated with mobile communications device 120. The warningsmonitor is, for example, a date, after which mobile communicationsdevice 120 will no longer be allowed to send data messages. The warningsmonitor is, as another example, a counter whose value is incremented ordecremented and checked to ensure that mobile communications device 120hasn't sent more than a maximum number of allowable data messages, afterthe maximum value has been exceeded, mobile communications device 120will be disallowed from sending data messages. The relay services node202 sends an enablement response to MCD 120 or host service 102 inresponse to a data message received from the one of MCD 120 or hostservice 102 and the enablement response could be one of a positiveacknowledgment, a negative acknowledgment, a warning message or theassociated mask. The enablement response allows the one of MCD 120 orhost services 102 to configure future data communications, includingdisabling future data communication, or simply allows MCD 120 or hostservice 102 to be aware of the result of the sent data message.

To initiate proper configuration of host service 102, communication 320is sent from host services 102 and passes information to relay services202. The information contained in communication 320 includes hostservice location and capability information. Relay services 202 storesand uses this information as a mask, in a database or a cache forexample. Relay services 202 uses, at least in part, the stored mask todetermine if future communications received from, or destined to, hostservices 102 will be allowed to pass, or will be negatively acknowledged(possibly with a warning) and possibly dropped.

Communication 325 is sent from relay services 202 in response tocommunication 320 and supplies a configuration block to host services102. This configuration block will be discussed in detail below, andincludes information for how host services 102 is to operate. Uponreceipt of communication 325, host services 102 will alter its operationto conform with the parameters and fields included in the configurationblock received in communication 325.

Communication 335 initiates a challenge-response conversation betweenmobile communications device 120 and relay services 202 whichestablishes security parameters and shares configuration information foruse by both MCD 120 and relay services 202. The security parameters andshared configuration information will be used by both MCD 120 and relayservice 202 to ensure that subsequent communications are secure andproper. The challenge-response conversation differs from theconversation comprising registration request 305 and registrationresponse 310 because the challenge-response conversation serves toestablish security parameters. There can exist some overlap betweeninformation exchanged during communications 305 and 310 and thechallenge-response conversation. Communication 340 indicates that relayservices 202 has received communication 335 and wishes to continue thechallenge-response conversation. As a response to communication 335,mobile communications device 120 issues communication 345. Communication345 shares a key used to secure further communications between MCD 120and relay services node 202, as well as to communicate MCD 120'scapabilities to relay services 202. The shared key is a subset of thedata which is included in communication 345 and is stored by both mobilecommunications device 120 and relay services 202 and is used as a keyfor scrambling or encrypting subsequent communications between mobilecommunications device 120 and relay services 202. The devicecapabilities included in communication 345, include the level of supportat which mobile communications device 120 is capable of cooperating withestablished protocols and methods and are stored by relay services 202for future use. In communication 350, relay services 202 will respond tocommunication 345 with a result. The result will include a configurationblock which is specific to MCD 120 and is to be used by MCD 120 to alterits mode of operation if required. This configuration block will bediscussed below, and includes information for how mobile communicationsdevice 102 is to behave.

As a result of communications 305, 320 and 345, provisioning system 218and relay services 202 have an accurate assessment of the state andstatus of both mobile communications device 120 and host services 120.Based on the information exchanged during the conversation described byFIG. 3, relay services 202 possesses stored masks which allow relayservice 202 to decide how to treat subsequent data messages which arereceived from, or destined to, either mobile communications device 120or host services 102. The above described conversation is meant only asan exemplary embodiment. Those in the art can appreciate differentconfigurations and orderings of this conversation. For example, it isnot necessary for 305 and 320 to occur in the order presented in FIG. 3.Any ordering or a different number of these communications would bepossible and are considered to be alternate embodiments.

The masks obtained and stored by relay services 202 during theconversation described in FIG. 3 enables relay services 202 to determinewhether mobile communications device 120 or host service 102 is enabledor disabled from sending and receiving certain types of communications.In one embodiment, if the mask which relay services 202 has stored andassociated with mobile communications device 120 indicates that mobilecommunications device 120 does not support a certain protocol at a highenough level, or is in an inappropriate location for a particularservice provided by host service 102, email or other data communicationsare blocked, effectively cutting mobile communications device 120 offfrom host service 102 for these types of communications. In anotherembodiment, if the mask which relay services 202 has stored andassociated with host service 102 indicates that host services 102 islocated in an inappropriate location or that it does not support arequired protocol at a required level, relay services 202 no longersends email or other data communications to host service 102 and relayservices 202 ceases forwarding email or other data communicationsreceived from host service 102. In yet another embodiment, relayservices node 202 has the ability to associate a specific MCD 120 with aspecific host service 102 and relay services node 202 uses one or bothof the masks stored and associated with MCD 120 and host service 102respectively to determine whether or not data communications will beallowed to or from either MCD 120 or host service 102. In a preferredembodiment, relay services 202 intercepts disallowed data communicationsand replies to the sender with a negative acknowledgment (or a warning)without sending the data communication to the intended recipient. Inanother embodiment, mobile communications device 120 and host services102 are informed by relay services 202 in a separate communication thatthey are not allowed to send certain types of data communicationsthrough relay services 202, and mobile communications device 120 andhost services 102 would no longer send those types of communications.

In the above description of FIG. 3, reference has been made to locationinformation in communication 305 and in communication 320. Locationinformation in these two communications is determined based onproperties of the communication in which the location information iscontained, such as the communication's source IP address, or based onproperties contained in the message itself, such as the identifier ofthe carrier network on which MCD 120 is operating or the networkprovider code supplied by MCD 120. With this information, it is possiblefor registration server 216, provisioning system 218 and relay services202 to accurately determine where the message's originator isgeographically located. A network provider code (NPC) can be acombination of certain network related information which is used to aidin determining the location of mobile communications device 120. Forexample, if mobile communications device 120 is operable in a GSMnetwork, the NPC is composed of the Mobile Country Code (MCC), theMobile Network Code (MNC) and an indicator of network type, if mobilecommunications device 120 is operable in a CDMA network, the NPC iscomposed of the SID and a network type indicator. The resolution oflocation is, for example, the result of looking up MCD 120's or hostservices 102's IP address in an IP address-to-country mapping stored ina storage means, such as a lookup table or database for example, or theresult of looking up MCD 120's NPC in a carrier-to-location mapping in astorage means, such as a lookup table or a database for example. Thegranularity of the location includes, but is not limited to, the countryin which either mobile communications device 120 or host services 102 islocated.

The configuration block which is communicated during communications 325contains fields which host services 102 uses to determine its ownbehavior and can for example contain the following fields:

Assume Capability Level: Instructs the host services 102 to assume thatmobile communications device 120 supports a particular capability level,until otherwise determined.

Default Message Type: Determines the default message type that hostservices 102 should send to mobile communications device 120 untilmobile communications device 120 instructs the host services 102 to senda different type. Values could indicate: send regular email; send oneenabling packet for each new email message destined for the mobilecommunications device 120; send one enabling packet for all pendingemail messages for the mobile communications device 120 and once themobile communications device 120 has polled to fetch this email, thehost services 102 may send another notification; or send no email to themobile communications device 120.

Batched Enabling Packet Format: Determines the message headers that thehost services 102 may put in an enabling packet sent to a mobilecommunications device 120 when it must send one enabling packet for allpending email. Values could indicate: the host services 102 may includethe Sender (From) header; the host services 102 may include theRecipient (To) header; the host services 102 may include the Subjectheader; the host services 102 may include the Subject header, but musttruncate it to 20 characters; or the host services 102 may include theMessage Reference ID; the host services 102 may include the messageBody.

Separate Enabling Packet Format: Determines the message headers that thehost services 102 may put in an enabling packet sent to the mobilecommunications device 120 when it may send one enabling packet for eachnew email message. Values could indicate: the host services 102 mayinclude the Sender (From) header; the host services 102 may include theRecipient (To) header; the host services 102 may include the Subjectheader; the host services 102 may include the Subject header, but musttruncate it to 20 characters; the host services 102 may include theMessage Reference ID; or the host services 102 may include the messageBody.

Send No Email To Non-Capable Mobile device: Determines if the hostservices 102 may send email or enabling packets to non-capable mobilecommunications devices 120. Values could indicate: host services 102 maysend email (or enabling packets) to mobile communications device 120that it knows do not support a particular protocol or feature; or hostservices 102 may not send email (or enabling packets) to mobilecommunications device 120 that it knows do not support a particularprotocol or feature.

The configuration block which is communicated during communications 350is used by mobile communications device 120 to determine behaviour andcould for example contain the following fields:

PIN Removal: Determines if the mobile communications device 120 mustremove the PIN from all message sent to the mobile communicationsdevice.

Conditional Poll Interval: Specifies the length of time betweenconditional polls performed by the mobile communications device 120.

Unconditional Poll Interval: Specifies the length of time betweenunconditional polls performed by the mobile communications device 120.

Login/Logout Required: Determines if the mobile communications device120 user must manually control sessions with the host services 102(login and logout).

Maximum Session Idle Time: Specifies the number of minutes before anidle mobile communications device 120 logs out.

Display Enables In Message List: Determines if the mobile communicationsdevice 120 puts placeholder messages in the message list for theenabling packets it receives.

Report Session Status: Determines if the mobile communications device120 must periodically report its session status to the host services102.

Action-Initiated Poll Allowed: Determines if the mobile communicationsdevice 120 may poll the host services 102 when the mobile communicationsdevice 120 performs a particular action (for example, turning on theradio, removing the mobile communications device 120 from its holster).

Manual Poll Allowed: Determines if the mobile communications device 120user may manually poll the host services 102 for new email.

P2P Subject Removal: Determines if the mobile communications device 120must remove the Subject header from all P2P traffic.

Extended Session Allowed: Determines if the mobile communications device120 can offer extended sessions to the mobile communications device 120user.

Modify Conditional Poll Interval Allowed: Determines if the mobilecommunications device 120 user is allowed to modify the conditional pollinterval (whether the mobile communications device 120 must provide auser interface option to facilitate this).

Polling Required: Determines if the mobile communications device 120must poll the host services 102 for new email.

Logged In Message Type Expected: Specifies the message type the mobilecommunications device 120 should expect to receive from the hostservices 102 when it is operating in the United States and has an opensession (logged in). Values could indicate: mobile communications device120 should receive regular email; mobile communications device 120should receive one enabling packet for each email message it has pendingat the host services 102; mobile communications device 120 shouldreceive one enabling packet when it has pending email at the hostservices 102; or mobile communications device 120 should receive noemail from host services 102.

Logged Out Message Type Expected: Specifies the message type the mobilecommunications device 120 should expect to receive from the hostservices 102 when it is operating in the United States but does not havean open session (logged out). Values could indicate: mobilecommunications device 120 should receive regular email; mobilecommunications device 120 should receive one enabling packet for eachemail message it has pending at the host services 102; mobilecommunications device 120 should receive one enabling packet when it haspending email at the host services 102; or mobile communications device120 should receive no email from host services 102.

One skilled in the art should appreciate that the various databases andservice logic processing set forth above with respect to the wirelesscommunications system may be realized in suitable hardware, firmwareand/or firmware logic blocks or in combination thereof. Furthermore, asalluded to before, the functionality of the relay network may also beintegrated within a wireless carrier network, whereby a “network node”may generally comprise the relay layer functionality as well.

What is claimed is:
 1. A method of operating a mobile device comprising: receiving an enable message indicating that a pending data message is available for retrieval from a host service; and communicating directly with the host service to retrieve the pending data message from the host service in response to receiving the enable message.
 2. The method of claim 1, wherein communicating directly with the host service comprises: sending a fetch message directly to the host service to retrieve the pending data message from the host service; and receiving the pending data message directly from the host service in response to sending the fetch message to the host service.
 3. The method of claim 1, further comprising opening a messaging application at the mobile device subsequent to receiving the enable message, wherein the messaging application is an electronic mail application.
 4. The method of claim 1, wherein the pending data message is an electronic mail message comprising a body of text.
 5. The method of claim 1, wherein the enable message is received from a relay services node.
 6. The method of claim 1, wherein the enable message comprises an identifier that identifies the pending data message.
 7. The method of claim 1, wherein communicating directly with the host service comprises retrieving a plurality of pending data messages from the host service after receiving the enable message.
 8. A mobile device comprising: a transceiver configured to receive an enable message indicating that a pending data message is available for retrieval from a host service; and a processor coupled to the receiver and configured to communicate directly with the host service to retrieve the pending data message from the host service in response to receiving the enable message.
 9. The mobile device of claim 8, wherein the processor is further configured to open a messaging application subsequent to receiving the enable message and prior to communicating directly with the host service.
 10. The mobile device of claim 8, wherein the transceiver is further configured to receive the pending data message after the enable message is received.
 11. The mobile device of claim 8, wherein the transceiver is further configured to: send a fetch message to the host service to retrieve the pending data message from the host service; and receive the pending data message from the host service in response to sending the fetch message to the host service.
 12. The mobile device of claim 8, wherein the transceiver is further configured to send a data message in response to receiving the pending data message.
 13. The mobile device of claim 8, wherein the enable message comprises an identifier that identifies the pending data message.
 14. A non-transitory computer readable medium storing instructions that enable communication with a mobile device via a wireless network, comprising: sending an enable message to the mobile device, wherein the enable message identifies a pending data message at the host service; and communicating directly with the mobile device to retrieve the pending data message from the host service in response to sending the enable message.
 15. The non-transitory computer readable medium of claim 14, wherein the instructions that enable communication with the mobile device via the wireless network further comprise: retrieving the pending data message subsequent to sending the enable message to the mobile device; and transmitting the pending data message to the mobile device.
 16. The non-transitory computer readable medium of claim 14, wherein the instructions that enable communication with the mobile device via the wireless network further comprise: receiving the pending data message before sending the enable message; and storing the data message before sending the enable message.
 17. The non-transitory computer readable medium of claim 14, wherein the instructions that enable communication with the mobile device via the wireless network further comprise opening a data session with the mobile device after sending the enable message.
 18. The non-transitory computer readable medium of claim 17, wherein the instructions that enable communication with the mobile device via the wireless network further comprise using the data session to transmit the data message to the mobile device.
 19. The non-transitory computer readable medium of claim 14, wherein the enable message comprises an identifier that identifies the pending data message.
 20. The non-transitory computer readable medium of claim 14, wherein the instructions that enable communication with the mobile device via the wireless network further comprise receiving a fetch message from the mobile device for the pending data message, and wherein the pending data message is retrieved in response to receiving the fetch message. 